Skip to content

Conversation

tim-schilling
Copy link
Member

Description

I considered using a named logger, but then realized we may run into issues where we're logging sensitive values unexpectedly in a project. It's probably better to remove this and just ask whoever when they are debugging to add a print statement (or similar).

Fixes #2171

Checklist:

  • I have added the relevant tests for this change.
  • I have added an item to the Pending section of docs/changes.rst.

Copy link
Member

@matthiask matthiask left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to me.

@matthiask
Copy link
Member

I don't know what's up with the failing test. Will investigate later.

@matthiask matthiask merged commit 5133f5f into main Aug 14, 2025
51 of 53 checks passed
@matthiask matthiask deleted the remove-logger branch August 14, 2025 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6.0 update, toolbar not working: DEBUG: debug_toolbar.store.The debug toolbar can't serialize
2 participants